Methods, systems, and computer readable media for detecting customer presence to initiate the ordering and purchase of goods and services

ABSTRACT

Methods, systems, and computer readable media for detecting customer presence to initiate the ordering and purchase of goods and services are disclosed. In one example, a system includes a detection server configured to detect the presence of a mobile device in a designated area associated with a merchant location and for initiating a menu selection application in the mobile device for placing an order for at least one product. The system further includes a merchant server configured to receive, from the mobile device, purchase order data associated with the order for the at least one product, a customer identifier associated with the mobile device, and a location identifier associated with the designated area, and for utilizing the customer identifier to send a notification message that indicates that the at least one product is available to the mobile device.

PRIORITY CLAIM

The present application is a continuation of U.S. patent applicationSer. No. 15/250,697, filed Aug. 29, 2016, which is a continuation ofU.S. patent application Ser. No. 13/220,360 (U.S. Pat. No. 9,430,786issued Aug. 30, 2016), which claims the benefit of U.S. ProvisionalPatent Application Ser. No. 61/377,786, filed Aug. 27, 2010, thedisclosure of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The subject matter described herein relates to the detection of wirelessdevices and triggering the wireless orders and purchases. Moreparticularly, the subject matter described herein relates to methods,systems, and computer readable media for detecting customer presence toinitiate the ordering and purchase of goods and services.

BACKGROUND

At present, a customer typically orders and purchases goods in-store orin a drive-thru window with the assistance of a human salesrepresentative or cashier. However, both of these options used bymerchant entities can prove to be quite cumbersome and expensive. Forexample, a customer must usually read through all the menu-optionsprovided by the merchant entity (e.g., a retail store, fast foodrestaurant, etc.) in order to decide which option he/she would like toorder and subsequently place an order at a point of sale counter mannedby a sales employee using a traditional payment instrument, such ascash, a check, or a payment card. This process is not automated and canbe inconvenient since the customer must interact with a salesperson thatmay make errors or may not be even be readily available at the point ofsale counter or drive-thru window when the customer is ready to place anorder for a product. Similarly, in many instances, a customer frequentlyvisits the same store on different occasions and orders the samegoods/service, yet must still order goods using means that require humaninteraction while placing the order.

Accordingly, there exists a need for methods, systems, and computerreadable media for detecting customer presence to initiate the orderingand purchase of goods and services.

SUMMARY

According to one aspect, the subject matter described herein includesmethods, systems, and computer readable media for detecting customerpresence to initiate the ordering and purchase of goods and services. Inone embodiment, a system includes a detection server configured todetect the presence of a mobile device in a designated area associatedwith a merchant location and for initiating a menu selection applicationin the mobile device for placing an order for at least one product. Thesystem further includes a merchant server configured to receive, fromthe mobile device, purchase order data associated with the order for theat least one product, a customer identifier associated with the mobiledevice, and a location identifier associated with the designated area,and for utilizing the customer identifier to send a notification messagethat indicates that the at least one product is available to the mobiledevice.

As used herein, the terms “wireless smart device” and “NFC enableddevice” may be synonymous and are intended to refer to any deviceenabled with near field communication (NFC), radio frequency (RF)communication, or barcode capturing capabilities to interact with asmart poster with the corresponding technology. In one aspect, wirelessdevice reader may include a radio frequency (RF) reader. One type ofwireless device that can wirelessly communicate to a wireless smartdevice reader is an NFC card or NFC handheld device, including but notlimited to a smart phone. In near field communication, a wireless smartdevice may communicate with a wireless transceiver or wireless devicereader via inductive coupling of the reader antenna to the deviceantenna. The two loop antennas effectively form a transformer. Thereader amplitude-modulates the radio frequency (RF) field to sendinformation to the device. The device communicates with the transceiverand/or reader by modulating the loading on the device antenna, whichalso modulates the load on the reader antenna. In a wireless smartdevice, the NFC handset may enable contactless payment, and a securityelement (SE) for ensuring secure transactions may be embedded, providedby a universal subscriber identity module (USIM), or provided as anadd-on to, for example, a SD or a jacket. Wireless smart devices maycommunicate with a transceiver or wireless device reader using NFC. Asused herein, the term “wireless communication” includes communicationconducted at ISO 14443 and ISO 18092 interfaces. These specificationsdefine communication protocols for wireless smart devices operating inclose proximity with a reader antenna.

The subject matter described herein may be implemented in software incombination with hardware or in software in combination with hardwareand firmware. For example, the subject matter described herein may beimplemented in software executed by a hardware based processor. In oneexemplary implementation, the subject matter described herein fordetecting customer presence to initiate the ordering and purchase ofgoods and services may be implemented using a non-transitory computerreadable medium to having stored thereon executable instructions thatwhen executed by the processor of a computer control the processor toperform steps. Exemplary non-transitory computer readable media suitablefor implementing the subject matter described herein include chip memorydevices or disk memory devices accessible by a processor, programmablelogic devices, and application specific integrated circuits. Inaddition, a computer readable medium that implements the subject matterdescribed herein may be located on a single computing platform or may bedistributed across plural computing platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the subject matter described herein will now beexplained with reference to the accompanying drawings, wherein likereference numerals represent like parts, of which:

FIG. 1 is a block diagram illustrating an exemplary system for detectingcustomer presence to initiate the ordering and purchase of goods andservices according to an embodiment of the subject matter describedherein;

FIG. 2 is a diagram illustrating the detection of consumer presence in aparking lot and the initiation of the ordering and purchase of goodsaccording to an embodiment of the subject matter described herein; and

FIG. 3 is a flow chart illustrating an exemplary process for detectingcustomer presence to initiate the ordering and purchase of goods andservices according to an embodiment of the subject matter describedherein.

DETAILED DESCRIPTION

FIG. 1 is a schematic diagram illustrating an exemplary system 100 forfacilitating the use of wireless smart devices to purchase products orservices according to an embodiment described herein. Referring to FIG.1, exemplary system 100 includes a mobile device 102 (e.g., a wirelesssmart device), a smart poster 116, an on-site merchant server 104 andassociated database 111, a detection system server 106, a backendmerchant server 110, a trigger management server (TMS) 105, a contentmanagement server (CMS) 109, and an over the air (OTA) provisioningserver 107. In one embodiment, mobile device 102 is a near fieldcommunications (NFC) enabled mobile device or smart phone. Although CMS109 and backend merchant server 110 are depicted as separate networkelements in FIG. 1, hardware and software components responsible for CMSfunctionality may be integrated in merchant server 110 without departingfrom the scope of the present subject matter.

Smart poster 116 may include any suitable object that displays oradvertises a particular product and is located in a place that isreadily accessible by potential consumers or purchasers of goods and/orservices. Smart poster 116 may be located inside and/or near a merchantestablishment. Although FIG. 1 only depicts a smart poster 116, anyother touch point (e.g., a radio frequency (RF) device reader located atan entrance, pickup area, parking spot, and a dining room table) may beused in system 100 without departing from the scope of the invention.For example, smart poster 116 may be located inside a restaurantestablishment (such as Starbucks® or McDonald's®), at a store entrance,on a store wall, in a shopping aisle, at a pickup area, at a diningtable, or other easily accessible location in or near the store. Inanother embodiment, a smart poster 116 may be located adjacent to anassociated parking area or parking spot near a merchant establishment.In one embodiment, smart poster 116 may advertise food items or menuselections (e.g., a fast food combination meal or item) as well asincluding a smart tag 118 that is configured to provide related menudata. For example, by containing menu data that is accessible to mobiledevice 102 via a near field communications (NFC) interfacing (e.g., anNFC tap), smart poster 116 may allow for convenient ordering andpurchasing options and thereby allowing consumers the option to bypassthe cashier line. In one embodiment, mobile device 102 may include ahardware based NFC circuit module 115 and may utilize NFC circuit module115 to interface with a smart tag 118 on smart poster 116 using nearfield communications.

In one embodiment, the present subject matter may be initiated upon thedetection of a customer's presence and mobile device 102. In oneembodiment, the customer's presence and mobile device 102 may bedetected upon mobile device 102 interfacing (via NFC) with a touchpoint, such as smart poster 116. Alternatively, the customer's presenceand mobile device 102 may be detected upon mobile device 102 entering adesignated area 108 via a detection system server 106 associated with amerchant location. Both of these embodiments may utilize a walletapplication 112 and/or menu selection application 114 stored in mobiledevice 102. In one embodiment, each of wallet application 112 and menuselection application 114 may include a software application or module(e.g., a MIDlet application) that is stored in memory 103 (either in asecure memory element and/or non-secure baseband memory) of mobiledevice 102, and when executed by a hardware based processor in mobiledevice 102 is capable of performing various functionalities. Forexample, wallet application 112 may utilize and manage multiplesoftcards stored on the mobile device, such as credit cards, debitcards, electronic loyalty cards, electronic loyalty reward certificates,electronic coupons, electronic tickets, and the like. Wallet application112 may also be used to communicate information to TMS 105 and receiveprovisioned data from OTA provisioning server 107. Payment credentials,such as electronic payment softcards including credit or debit cards mayalso be stored in any suitable user defined priority within walletapplication 112. For example, a user can configure wallet application112 such that a Visa® debit card is always used as a firstchoice/priority. Alternatively, wallet application 112 may be programmedto use certain electronic payment softcards under certain conditions.For example, wallet application 112 may be programmed to conduct apurchase transaction using a Macy's® softcard (e.g., an electronicsoftware based card stored and displayed via device 102) when in aMacy's® store. GPS triangulation, GSM triangulation, or WiFitriangulation methods applied to mobile device 102 could be used todetermine when mobile device 102 is present in a certain location, suchas a Macy's® store (e.g., when device 102 is interfaces with a wirelessreader in) Macy's®. User preferences can be used to prioritizeelectronic softcards residing within wallet application 112. Walletapplication 112 may also comprise an algorithm for submitting and payingfor the order downloaded from smart poster 116. In one embodiment,wallet application 112 may, alone or with menu selection application114, present the user with the following options upon being detected bysystem 100 (e.g., interfacing with a smart poster or an RF reader, orupon detection by detection system server 106): (i) the option to “Orderand Pay”, or (ii) the option to “Create and Submit Order” as describedbelow. In one embodiment, menu selection application 114 (via wallet112) to allow the customer to interface with mobile device 102 and placean order for meal/food/coffee/general products package(s) using menudisplayed on the mobile device screen as well as to select individualitems to add to the pre-defined meal, food item, beverage item, andgeneral products package after mobile device 102 is detected by system100. In one embodiment, consumers may select an option on the mobiledevice wallet 112 and/or menu selection application 114 to obtaininformation on each product displayed or listed on menu to getinformation or even obtain a related coupon/offer. In one embodiment,both the wallet application 112 and menu selection application 114 mayinclude software applications that reside in a memory 103 or hardwarestorage component in mobile device 102 that may be executed by ahardware processor (not shown) in mobile device 102. In one embodiment,memory 103 may comprise at least one of a secure memory element and/or anon-secure baseband memory.

In one embodiment, mobile device 102 may be detected when the userinterfaces mobile device 102 (e.g., taps) with the order menu displayedon smart poster 116, wherein each menu item on the order menu isassociated with a smart tag 118 that comprises a passive NFC or RF tagdevice (e.g., a circuit device or wireless transceiver) that is poweredby an interfacing mobile device 102. For example, after mobile device102 is tapped or brought in close proximity with smart tag 118, smarttag 118 may be activated by obtaining power from the electromagneticfield generated by mobile device 102. In other embodiments, smart tag118 may include an active RF tag or reader equipped with its own powersource (e.g., a battery). Whether passive or active, smart tag 118 iscapable of communicating smart poster content information to aninterfacing mobile device 102. In one embodiment, the smart postercontent information may include a product selection identifier (e.g., amenu item identifier), a content provider code (CLC), a tag locationcode (TLC), and a location identifier (e.g., an IP address, a URL, aURI, and the like) associated with TMS 105, all of which may be providedto a mobile device 102 via NFC. In an alternative architecture, thelocation identifier may be associated with one or more contentmanagement servers 109 or a backend merchant server 110.

Mobile device 102 may initiate a wallet application 112 upon interfacingwith smart tag 118 on smart poster 116. In one embodiment, smart poster116 advertises a single menu item/product or selection of menuitems/products (e.g., a specific sandwich, a specific beverage, or anumber of combo meals). In such an embodiment, mobile device 102 can tapthe predefined menu selection displayed on smart poster 116 and receiveinformation including a content product code, a location identifier(e.g., URL, IP address, or URI) associated with TMS 105. In oneembodiment, each menu item selection displayed on smart poster 116 has acorresponding smart tag for interfacing. A consumer may trigger walletapplication 112 to download a product selection identifier (e.g.,corresponding to a desired menu item, such as a predefined meal package,a predefined beverage item, and a predefined food item), a TLC (which,e.g., discloses the location of the smart poster), and an associated CPC(which, e.g., identifies the merchant entity and/or the menu itemcontent data to be downloaded to and displayed on mobile device 102) fora specific menu option by interfacing mobile device 102 with at leastone smart tag 118 on smart poster 116.

In one embodiment, wallet application 112 may use a location identifier(e.g., a URL, URI, or IP address) contained in smart poster 116 tocommunicate with trigger management server 105 or backend merchantserver 110 in order to obtain menu/product content and displayinformation (e.g., mobile device-specific content and displayinformation for a la carte menu items, sizes, quantities, etc.)regarding a particular product. For example, a wallet application 116may be configured to contact a trigger management server 105 using thelocation identifier and provide TMS 105 with a CLC. TMS 105 may use theCLC to determine the appropriate content management server (CMS) capableof accessing the desired content data (e.g., menu item content data)advertised by smart poster 116. Once the appropriate CMS (e.g., CMS 109)is determined, TMS 105 forwards the CLC along with the customeridentifier to CMS 109. Using the CLC, CMS 109 may then contact theappropriate content provider (i.e., backend merchant server 110) andobtain the desired menu content data by providing the associated menuitem identifier. For example, merchant server 110 may use the CLC toaccess and extract menu/product content data from a content database 111and subsequently provide the content data to CMS 109. Upon receiving thedesired menu content data, CMS 109 then provides the desired menucontent data along with the customer phone number (e.g., customeridentifier) to OTA provisioning server 107, which then downloads themenu content data to be displayed mobile device 102. At that point,mobile device 102 may display the menu content data and prompt thecustomer with two options: “Order and Pay” or “Create and Submit Order”.

In one embodiment, the “Order and Pay” option may be selected towirelessly communicate the order and payment information and a customeridentifier (e.g., mobile phone number) to backend merchant server 110(via TMS 105 and CMS 109) to initiate a purchase transaction. If themobile device 102 is used to select the “Order and Pay” option, wallet112 sends at least the menu item identifier, a customer identifier(e.g., the mobile device phone number), and payment credentials tomerchant server 110. In one embodiment, payment credentials are based oneither a default softcard setting for any payment or based on a paymentoption that is predefined by the merchant store. If both payment optionsare set, then the payment option predefined for the specific store takesprecedence. If no payment option is set, the user of mobile device 102will be prompted to select a payment instrument from a list of paymentcredential instruments mobile device 102 has in wallet 112. In oneembodiment, payment credential data to be used in the purchasetransaction is provided by wallet application 112 to backend merchantserver 110 via TMS 105 and CMS 109. Backend merchant server 110 is thenresponsible for communicating with payment servers (not shown) toproperly conduct proper payment procedures. After a successful transferof funds, backend merchant server 110 may communicate a messageindicating a successful purchase transaction to CMS 109, which in turnnotifies mobile device 102 via OTA provisioning server 107.

Alternatively, upon selection of the “Create and Submit Order” option,the consumer is presented with choices and can make the appropriate menuselections. The menu selection or order, payment credentials, and thephone number of NFC enabled device 102 can then be communicated tomerchant server 110 (via TMS 105 and CMS 109) for processing. Anexemplary purchase credential may include an electronic payment softcardresiding in wallet application 116. If no payment option is set, theuser may be prompted to select a payment instrument from the list ofpayment instruments available in wallet application 116. Notably, thepurchase for the desired product is conducted in a manner that bypasses(or obviates the need for) a payment register and/or cashier in a retaillocation of the merchant (e.g., without interacting with a sales clerkand/or without the use a payment register or point of sale terminal).Like with the “Pay and Order” option, payment credential data to be usedin the purchase transaction involving the “Create and Submit Order”option is provided by wallet application 112 to backend merchant server110 via TMS 105 and CMS 109. Backend merchant server 110 is thenresponsible for communicating with payment servers (not shown) toproperly conduct proper payment procedures. After a successful transferof funds, backend merchant server 110 may communicate a messageindicating a successful purchase transaction to CMS 109, which in turnnotifies mobile device 102 via OTA provisioning server 107.

In another embodiment, NFC enabled device 102 can customize an order byeither 1) modifying a specified menu selection or 2) tap to download ana la carte menu and specify choices. For either method, users may selectthe “Create and Submit Order” option on mobile device 102. For ordersthat give the consumer the option to specify their preferences, the usermay be able to download the order, modify the order (or create a neworder), and submit the customized order along with payment credentialsto merchant server 110. For example, if the mobile device 102 is used toselect the “Create and Submit Order” option, the user is enabled tomodify the existing order. Afterwards, wallet 112 submits the modifiedorder identification, a customer identifier (e.g., the mobile devicephone number), and payment credentials to the merchant server 110 (viaTMS 105 and CMS 109). In one embodiment, payment credentials are basedon either a default card setting for any payment or based on a paymentoption that is predefined by the merchant store. If both payment optionsare set, then the payment option predefined for the specific store takesprecedence. If no payment option is set, the user of mobile device 102will be prompted to select a payment instrument from a list of paymentinstruments mobile device 102 has in wallet 112.

In one embodiment, mobile device 102 may be detected when mobile device102 is brought within a designated area 108 associated with a merchantlocation. In such embodiments, the customer of mobile device 102 mayregister with the merchant and provide a registered/recognizableidentifier associated with mobile device 102 such that a detectionsystem server 106 may be permitted to wirelessly detect mobile device102. In an alternate embodiment, a hardware component (e.g., a hardwarecircuit) may be added to mobile device 102 to enable detection by system106.

For example, designated area 108 may include a store location, a parkingspot location, a parking lot location, and the like. Designated area 108may be defined and monitored by a detection system server 106 thatutilizes WiFi-based, global systems for mobile communications(GSM)-based, Bluetooth-based (e.g., Bluetooth handshaking),cellular-based, and/or global positioning system (GPS) basedtechnologies. For example, detection system server 106 may include aWiFi based router associated with a merchant entity may detect thepresence of a consumer's mobile device 102 within a WiFi range, i.e.,designated area 108. Mobile device 102 may utilize a service setidentifier (SSID) associated with detection system server 106 andprovide an identifier that is recognized by system 106. In anotherembodiment, WiFi, cellular and or GPS positioning solutions usingtriangulation may be employed to detect mobile device 102. For example,detection system server 106 may include a plurality of routers that uponcommunicating with (e.g., upon receiving one or more customer presencesignals that include an SSID and recognizable mobile device identifier)mobile device 102, may determine the position of mobile device 102 andbe generate an alert to a merchant server upon entering a designatedarea (e.g., entering a store, a parking lot, or a specific parkingspot).

Once identified/detected in a parking lot or at the store/restaurantentrance, detection system server 106 may communicate directly with TMS105. For example, detection system server 106 may provide a customeridentifier, a merchant identifier, and location information associatedwith mobile device 102 to TMS 105 and/or CMS 109. For example, CMS 109may then use the merchant identifier to communicate with backendmerchant server 110, which in turn utilizes the customer identifier todetermine 1) if an order associated with the customer identifier hasbeen previously placed (either via a website or mobile device), 2) if astored “usual order” associated with the customer identifier is savedwith backend merchant server 110 or in wallet application 112 and/or 3)if the mobile device 102 associated with the customer identifier hasbeen registered as having a smartphone application (e.g., a menuselection application 114).

Upon determining that an order has been previously made, backendmerchant server 110 may query mobile device 102 whether the order shouldnow be processed via CMS 109 and OTA provisioning server 107. Forexample, OTA provisioning server 107 may query mobile device using anover the internet (OTI) server path/channel to mobile device 102 sincethe query comprises low security data. Notably, the OTI channel allowsfor faster communication with low security overhead. In an alternateembodiment, backend merchant server 110, TMS 105, and/or CMS 109 maydirectly communicate with mobile device 102.

Upon determining that a customer has a pre-stored/saved order, backendmerchant server 110 may query mobile device 102 whether the usual ordershould be processed via CMS 109 and OTA provisioning server 107. Forexample, database 111 may be used to store saved orders previously madeby a registered consumer.

Similarly, upon determining that mobile device 102 does not have a menuselection application 114, backend merchant server may utilize OTAprovisioning server 107 to query the mobile device 102 if a menuselection application is desired. For example, OTA provisioning server107 may query mobile device using an over the internet (OTI) serverpath/channel to mobile device 102 since the query comprises low securitydata. Notably, the OTI channel allows for faster communication with lowsecurity overhead. In an alternate embodiment, backend merchant server110, TMS 105, and/or CMS 109 may directly communicate with mobile device102. Similarly, if the user of mobile device 102 answers in theaffirmative to download the offered menu selection application 114, asignal message is sent directly to TMS 105, CMS 109, or merchant backendserver 105. The signal message may be sent via an OTA channel, an OTIchannel, or a WIFI channel.

In one embodiment, the user may also save an order within memory 103(e.g., wallet application 112 and/or menu selection application 114) forfuture reordering purposes. This is advantageous as orders can be reusedwithout having to be recreated or reselected. In this embodiment, theconsumer may use NFC enabled device 102 to specify choices from variousmenu item choices, sizes, and details of the product using walletapplication 112 and/or menu selection application 114. The consumer maystore the predefined order with an associated payment credential. Thisfeature also simplifies the ordering process thereby saving consumerstime. For example, the consumer may be notified about saved or storedorders previously placed with a given merchant, the user then has theflexibility to submit the same order or place a new order. Saved orstored orders may also be modified and resubmitted with new preferences,for example, a previous order of a hamburger cooked medium could bechanged to medium-well. The new order can then be saved to NFC enableddevice 102. Notably, the user of mobile device 102 may be queried as towhether the saved usual order is to be placed upon mobile device 102being detected by detection system server 106 (e.g., entering designatedarea 108 and/or via detection by WiFi triangulation). Alternatively, apre-stored order in mobile device 102 may be triggered to be processedupon tapping on (e.g., NFC interfacing with) smart poster 116 or tappingon an RF device reader at the point of sale. Also, a pre-stored order inmobile device 102 may be triggered via a menu driven screen that may beinstalled at a dining table, pick up area, or any other location in therestaurant or store.

FIG. 2 depicts an exemplary embodiment in which consumer presence isdetected in a parking lot and the initiation of the ordering andpurchase of goods via a mobile device according to an embodiment of thesubject matter described herein. In one embodiment, a merchant locationsuch as restaurant 208 may be located near a parking lot area with aplurality of parking spaces 212-216. Each of parking spaces 212-216 maybe equipped with its own parking spot touch point 202-206. Each ofparking space touch points 202-206 may be equipped with at least onesmart tag 222-226.

In one embodiment, a mobile device 102 is carried into or turned on in adesignated service area (not unlike area 108 depicted in FIG. 1). Adetection system server 106 in restaurant 208 may be used to monitor anddefine a designated area 108 by utilizing the range of WiFi-based,GSM-based, Bluetooth-based, cellular-based, and/or global positioningsystem (GPS) based technologies. For example, detection system server106 may include a WiFi based router associated with a merchant entitymay detect the presence of a consumer's mobile device 102 within a WiFirange, e.g., area surrounding restaurant 208.

Mobile device 102 may utilize a service set identifier (SSID) associatedwith detection system server 106 and provide an identifier that isrecognized by system 106. In another embodiment, detection system server106 may utilize WiFi triangulation, cellular triangulation and or GPStriangulation solutions to detect mobile device 102. For example,detection system server 106 may include a plurality of WiFi routers thatupon communication with (e.g., upon exchanging WiFi signals that includean SSID and recognizable mobile device identifier) mobile device 102,may determine the position of mobile device 102. If mobile device 102enters the restaurant 208 or is located in a particular parking spot(e.g., parking spot 212), detection system server 106 may generate analert message to on-site merchant server 104 (not shown in FIG. 2) toindicate the location of mobile device 102. For example, certain WiFi orGPS coordinates may be predefined to correspond with a particularparking space or the entrance of restaurant 208. In one embodiment, auser of mobile device 102 may use an application to initiatecommunication (i.e., initiate the detection process) with detectionsystem 106 after parking in any of parking spaces 212-216. After mobiledevice 102 is identified/detected in a parking space or at thestore/restaurant entrance, on-site merchant server may communicatedirectly with TMS 105 in the manner described above.

In an alternate embodiment, a customer may park an automobile in any oneof parking spaces 212-216 and, from the automobile, use a mobile device102 to interface with a respective parking space touch point 202-206.For example, if a customer parked in parking space 212, the customer mayview the parking space touch point 202 that displays a number of menuitem selections (e.g., a predefined fast food combo meal, a single fooditem, a single beverage, or any combination thereof). The user mayinterface mobile device 102 with smart tag 222 that corresponds to thedesired menu item. For example, the consumer may tap mobile device 102on the ordering menu board to place the order for a pre-defined menuoption package (e.g., a combination of food and/or beverage items) orselect individual items to add to the pre-defined meal package or toform a complete new order. Consumers are able to select an option ontheir mobile device's wallet 112 and/or menu selection application 114to obtain information on each product displayed or listed on the menu torequest information or a related electronic coupon/offer. Although onlyone smart tag 222 is shown in FIG. 2, any number of smart tags(corresponding to any number of menu items) may be situated on parkingspace touch point 202 without departing from the scope of the presentsubject matter. Once the menu item(s) corresponding with the smart tagsare tapped (i.e., NFC interfacing), wallet application 112 on mobiledevice 102 communicates with TMS 105 in the manner described above.However, in this embodiment, the tag location identifier may bespecifically associated with a parking spot 212.

FIG. 3 is a flow chart illustrating an exemplary process 300 fordetecting customer presence to initiate the ordering and purchase ofgoods and services according to an embodiment of the subject matterdescribed herein. In block 302, the presence of a mobile device isdetected. In one embodiment, a detection system server 106 (as shown inFIG. 1) at a merchant location may detect the presence of a mobiledevice. For example, mobile device 102 may be carried into or turned onin designated area 108 that is associated with a merchant store.Designated area 108 may be a WiFi service area that is created by asimple range-based WiFi detection system server 106 in a merchant store.In one embodiment, the designated area 108 is defined by the range of aWiFi router. For example, the designated are may include the merchantstore and/or a store parking lot (or at least a portion thereof) that iscontained within the range of a WiFi router. In an alternate embodiment,detection system server 106 may utilize a plurality of routers to detectthe presence of the mobile device via WiFi triangulation. In yet anotherembodiment, cellular (e.g., GSM) triangulation and/or GPS triangulationsolutions may be employed to detect the presence of a registered mobiledevice. Notably, detection system server 106 is configured to recognizea consumer's mobile device presence in a designated area (e.g., a storeentrance or a parking lot space). In yet another embodiment, mobiledevice 102 may be interfaced with or tapped on a smart poster inmerchant store 204 or other area (e.g., a smart poster located at aparking space).

In one embodiment, a merchant entity may provide a WiFi based detectionsystem 106 to recognize the presence of a consumer's mobile device inits parking lot or at the store/restaurant entrance and initiate adialogue with customers to allow them to place an order for pre-definedmeal/food/coffee/general products package(s) menu displayed on themobile device screen as well as to select individual items to add to thepre-defined meal/food/coffee/general products package. Consumers shouldbe able to select an option on the mobile device wallet to getinformation on each product displayed or listed on menu to getinformation or get a coupon/offer for.

In block 304, a menu selection application in the mobile device isinitiated. In one embodiment, wallet 112 in mobile device 102 istriggered to execute (along with a hardware based processor) a menuselection application 114. Wallet application 112 may be triggeredeither by a signal message from OTA provisioning server 107 or by mobiledevice 102 interfacing with a touch point (e.g., smart poster 116). Forexample, a consumer may enter a merchant store offering goods and/orservices advertised from pre-defined menus. The consumer may tap a smarttag corresponding to a specific menu option which downloads the order tomobile device 102. This action prompts the wallet application 112 and/ormenu selection application 114 to execute and prompt the user with“Order and Pay” option or the “Create and Submit Order” as disclosedabove. The user's selection of either option sends the order and thepayment credential information, via TMS 105 and/or CMS 109, to a backendmerchant server 110 (e.g., a store ordering system) to process the orderand the payment.

In block 306, purchase order data, a customer identifier, and a locationidentifier is received. In one embodiment, merchant server 110 receivesthe purchase order data (i.e., the payment credential data and theproduct selection identifier) from mobile device 102 either directly orvia TMS 105 and/or CMS 109 (depending on the location identifierURI/URL/IP address). Merchant server 110 may also receive purchase orderdata, a customer identifier (e.g., a mobile phone number) associatedwith the mobile device 102, and a location identifier associated withthe service area 108 (e.g., a store location or a parking spotlocation). Once backend merchant server 110 receives the paymentcredential data, customer identifier, and product selection identifier(e.g., menu item selection identifier), merchant server may initiate thepurchase transaction.

In block 308, the purchase transaction is processed. In one embodiment,payment credential data to be used in the purchase transaction isprovided by wallet application 112 to backend merchant server 110 viaTMS 105 and CMS 109. Backend merchant server 110 is then responsible forcommunicating with payment servers (not shown) to properly conductproper payment procedures. After a successful transfer of funds, backendmerchant server 110 may communicate a message indicating a successfulpurchase transaction to CMS 109, which in turn notifies mobile device102 via OTA provisioning server 107. Backend merchant server 110 mayalso notify on-site merchant server 104 of the successful purchasetransaction by sending a notification message that includes at least thecustomer identifier, payment amount information, and the menu itemselection identifier. The successful purchase transaction notificationmay also be provided to a point of sale machine at the merchant locationby on-site merchant server 104.

In block 310, a notification message indicating that the product isavailable is sent. For example, when the product is prepared and/orready to be delivered by the merchant entity, on-site merchant server104 associated with the store location (e.g., restaurant, fast foodrestaurant, retail store, or merchant entity) sends a notificationmessage (e.g., SMS/MMS or email) to the customer's mobile phone 102 thatthe purchased product (e.g., food item, beverage item, combo meal,groceries, general merchandize, etc.) is ready to be picked up from themerchant location (e.g., inside the store or a drive-thru window, or adesignated parking space). Alternatively, the notification message sentto the consumer's mobile device 102 may indicate that the product isavailable and will be delivered to the specific parking spot or tableindicated by the associated location identifier. In one embodiment, thecustomer identifier is utilized to send the notification message.

It is understood that various details of the presently disclosed subjectmatter may be changed without departing from the scope of the presentlydisclosed subject matter. Furthermore, the foregoing description is forthe purpose of illustration only, and not for the purpose of limitation.

What is claimed is:
 1. A system for detecting customer presence toinitiate the ordering and purchase of goods and services, the systemcomprising: a trigger management server (TMS) configured to receive acustomer identifier associated with a mobile device and purchase orderdata including payment credential data and a product selectionidentifier for an order of at least one product from the mobile device,wherein an identifier associated with the TMS and the product selectionidentifier is received by the mobile device upon interfacing with asmart tag and wherein the payment credential data includes electronicpayment softcard data that originates in a wallet application stored inmemory in the mobile device; and a backend merchant server configured toreceive the purchase order data and the customer identifier from the TMSand to utilize the customer identifier to send a notification message tothe mobile device indicating that the at least one product is available.2. The system of claim 1 wherein the interfacing with a smart tagincludes wirelessly communicating via a near field communications (NFC).3. The system of claim 1 wherein interfacing with the smart tag includeswirelessly communicating via barcode capturing capabilities.
 4. Thesystem of claim 1 wherein the product selection identifier includes atleast one identifier associated with a predefined meal package, apredefined beverage item, and a predefined food item.
 5. The system ofclaim 1 wherein the smart tag is located at a parking spot.
 6. Thesystem of claim 1 wherein the backend merchant server uses theidentifier to determine a designated location in which the at least oneproduct is to be delivered.
 7. The system of claim 1 wherein the mobiledevice interfacing with the smart tag triggers a menu selectionapplication in the mobile device to display a menu selection associatedwith the at least one product.
 8. The system of claim 7 wherein the menuselection application in the mobile device enables a user of the mobiledevice to modify features of the menu selection.
 9. A method fordetecting customer presence to initiate the ordering and purchase ofgoods and services, the method comprising: receiving, by a triggermanagement server (TMS) from a mobile device, a customer identifierassociated with the mobile device and purchase order data that includespayment credential data and a product selection identifier for an orderof at least one product, wherein the mobile device previously obtainsboth an identifier associated with the TMS and the product selectionidentifier upon interfacing with a smart tag and wherein the paymentcredential data includes electronic payment softcard data thatoriginates in a wallet application stored in memory in the mobiledevice; and sending, by the TMS, the purchase order data and thecustomer identifier to a backend merchant server, wherein the backendmerchant server is configured to utilize the customer identifier to senda notification message to the mobile device that indicates that the atleast one product is available.
 10. The method of claim 9 wherein theinterfacing with a smart tag includes wirelessly communicating via anear field communications (NFC).
 11. The method of claim 9 whereininterfacing with the smart tag includes wirelessly communicating viabarcode capturing capabilities.
 12. The method of claim 9 wherein theproduct selection identifier includes at least one identifier associatedwith a predefined meal package, a predefined beverage item, and apredefined food item.
 13. The method of claim 9 wherein the smart tag islocated at a parking spot.
 14. The method of claim 9 comprising usingthe identifier to deliver the at least one product to a designatedlocation.
 15. The method of claim 9 wherein initiating a menu selectionapplication in the mobile device further comprises displaying a menuselection associated with the at least one product.
 16. The method ofclaim 15 wherein initiating the menu selection application in the mobiledevice further comprises triggering a menu selection application in themobile device that enables a user of the mobile device to modifyfeatures of the menu selection.
 17. A non-transitory computer readablemedium having stored thereon comprising computer executable instructionsthat when executed by a processor of a computer performs stepscomprising: receiving, by a trigger management server (TMS) from amobile device, a customer identifier associated with the mobile deviceand purchase order data that includes payment credential data and aproduct selection identifier for an order of at least one product,wherein the mobile device previously obtains both an identifierassociated with the TMS and the product selection identifier uponinterfacing with a smart tag and wherein the payment credential dataincludes electronic payment softcard data that originates in a walletapplication stored in memory in the mobile device; and sending, by theTMS, the purchase order data and the customer identifier to a backendmerchant server, wherein the backend merchant server is configured toutilize the customer identifier to send a notification message to themobile device that indicates that the at least one product is available.18. The non-transitory computer readable medium of claim 17 wherein theinterfacing with a smart tag includes wirelessly communicating via anear field communications (NFC).
 19. The non-transitory computerreadable medium of claim 17 wherein interfacing with the smart tagincludes wirelessly communicating via barcode capturing capabilities.20. The non-transitory computer readable medium of claim 17 whereininitiating a menu selection application in the mobile device furthercomprises displaying a menu selection associated with the at least oneproduct.